Method and system for the transfer of communication network administration information

ABSTRACT

In order to minimize a bandwidth required for the transfers of communication network administration information, said information relating to objects pertaining to hardware, software or network operation elements, catalogued in an administration information base ( 11 ) and with each of which is associated a formal language specification, the system comprises a translator module ( 10 ). The module ( 10 ) is designed to generate on the basis of the specification for each object, a pair of words the value of whose first word pertains to an indication of the object and the value of whose second word pertains to an information length of the object. The module ( 10 ) is also designed to generate one or more templates comprising an ordered set of pairs of words and an identifier, making it possible to subsequently send an ordered string of information corresponding to each template.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is the U.S. national phase of the International PatentApplication No. PCT/FR2004/002271 filed Sep. 7, 2004, which claims thebenefit of French Application No. 03 11345 filed Sep. 26, 2003, theentire content of which is incorporated herein by reference.

FIELD OF THE INVENTION

The field of the invention is that of the administration ofcommunication networks. The term administration is to be taken here inits widest sense, that is to say it relates both to configuration andmanagement, or even to the control of the equipment of communicationnetworks.

BACKGROUND OF THE INVENTION

To configure an item of equipment, it is for example possible to use aninteractive interface protocol such as the known TELNET protocol. Thisprotocol is standardized but the data accessible are not. This poses aproblem, in particular in respect of a considerable amount of networkequipment as is often the case.

Among other things, management comprises the prediction and detection offaults. In the known state of the art, mention may be made by way ofexample of document WO 02/46928 which discloses a system which processesinformation obtained from sensors associated with variables cataloguedin an administration information base named MIB (Management InformationBase). To allow its interpretation and large-scale processing inrelation to numerous items of equipment, the definitions of thevariables are specified by means of a standardized language named SMI(Structure of Management Information). A protocol named SNMP (SimpleNetwork Management Protocol), likewise standardized, makes it possibleto access the variables by exchanging queries/responses betweenequipment of the network.

As is the case for example in document WO 02/17094, the variables mayrelate to devices which are rather sensors of temperature, alarm statesor IP type network addresses than more complex equipment. For suchdevices, one then speaks of objects catalogued in one or more variousMIBs. This document discloses means for interfacing the devices underSNMP.

The technique based on the SNMP/SMI/MIB trio has reached a certaindegree of maturity. The specifications of the MIBs themselves and alsothose of the objects catalogued therein, are specified both in terms ofsemantics and size. The formulation of the MIBs is fine-tuned, possiblyby means of automated handlers such as those proposed for example indocument U.S. Pat. No. 6,009,431. The absolute identification of theobjects by the standards (X208 and X209), the absolute identification ofthe instances of objects by the instance index, imply that the MIBsprovide a normative benchmark prized by operators. The SNMP protocol iswidely used for numerous types of equipment and services such asattested to by documents WO 01/44924, EP 115 8720 or else WO 02/47322.

However, the SNMP protocol is not satisfactory for transporting asizeable volume of data since it adds a considerable overhead in termsof additional information. The queries/responses mode (polling) makes itdifficult to optimize the internal management of the data in the networkequipment. The growth in the communication throughput of equipment isaugmenting the risk of mantissa overshoot in computers with the cascadeeffect of consequently increasing the frequency of queries/responsesthat is required in order to avoid this overshoot of mantissas. Theexchanging of the identifiers of instances between machines,considerably increases the bandwidth required, to a first approximationby a factor of three, to the detriment of the useful bandwidth for thedata of the users. Although approximately 85% of the objects of the MIBsare fields of tables, although approximately 99.9% of the instances areinstances of these objects, that is to say of fields of tables, the SNMPprotocol does not optimize the consultation of the tables. While thefields of a table row have the same index, the SNMP protocol repeats theindex for each field, thus adding an extra throughput of around onehundred bytes per table row consulted.

OBJECTS OF THE INVENTION

An object of the invention is a method for minimizing a bandwidthrequired for the transfers of communication network administrationinformation, said information relating to objects pertaining tohardware, software or network operation elements, catalogued in anadministration information base and with each of which is associated aformal language specification.

SUMMARY OF THE INVENTION

The method is noteworthy in that it comprises steps consisting in:

-   -   generating on the basis of said specification for each object, a        pair of words the value of whose first word pertains to an        indication of the object and the value of whose second word        pertains to an information length of the object;    -   constructing a template comprising an ordered set of pairs of        words generated and an identifier of said template, making it        possible to subsequently send an ordered string of information        corresponding to said template.

More particularly, the method comprises steps consisting in:

-   -   traversing a tree of the administration information base each        node of which is associated with an object;    -   testing at each node whether the object is of scalar or table        type;    -   constructing the template by appending the word pair generated        to the template if the object is of scalar type;    -   constructing another so-called table template if the object is        of table type for the objects of the table.

Advantageously, the method comprises steps consisting in constructing inaddition a configuration template comprising the pairs of wordsgenerated for objects with modifiable access.

An object of the invention is also a system for minimizing a bandwidthrequired for the transfers of communication network administrationinformation, said information relating to objects pertaining tohardware, software or network operation elements, catalogued in anadministration information base and with each of which is associated aformal language specification.

The system is noteworthy in that it comprises a translator moduledesigned to generate on the basis of said specification for each object,a pair of words the value of whose first word pertains to an indicationof the object and the value of whose second word pertains to aninformation length of the object and to generate a template comprisingan ordered set of pairs of words and an identifier, making it possibleto subsequently send an ordered string of information corresponding tosaid template.

More particularly, the translator module is designed to traverse a treeof the administration information base each node of which is associatedwith an object, so as to test at each node whether the object is ofscalar or table type and to construct the template by appending the wordpair generated to the template if the object is of scalar type orconstruct another so-called table template if the object is of tabletype for the objects of the table.

Advantageously, the translator module is designed to construct inaddition a configuration template comprising the pairs of wordsgenerated for objects with modifiable access.

For example, the system comprises a supervisor module designed tocollect measurements and an exportation module designed to transmit atleast one ticket of data pertaining to these measurements to a server,preceding it with the template of this data ticket.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be better understood on the basis of the exemplaryimplementation described hereinbelow with reference to the appendeddrawings, in which:

FIG. 1 is a system diagram in accordance with the invention;

FIGS. 2 to 7 show method steps in accordance with the invention;

FIG. 8 represents a tree structure for a particular object of tabletype;

FIG. 9 shows a template of the object represented in FIG. 8;

FIG. 10 shows an exemplary data ticket, in accordance with the templateof FIG. 9;

FIG. 11 represents a tree structure for another particular object oftable type;

FIG. 12 shows a template of the object represented in FIG. 11;

FIG. 13 shows an exemplary data ticket, in accordance with the templateof FIG. 12;

FIG. 14 is a diagram of possible industrial application;

FIG. 15 shows a table template generated by the system of FIG. 14;

FIG. 16 shows an exemplary data ticket, in accordance with the templateof FIG. 15;

FIG. 17 shows another table template generated by the system of FIG. 14;

FIGS. 18 a to 18 c show an exemplary data ticket, in accordance with thetemplate of FIG. 17.

MORE DETAILED DESCRIPTION

In the system described hereinbelow with reference to 1, a translator 10comprises means of communication with a network 16 with a view toreceiving commands and to transmitting data. The translator 10 is amachine such as for example a computer comprising a processor andprograms required for implementing the method steps described later withreference to FIGS. 2 to 6. The translator 10 comprises means of readingfrom databases 11 and 15, means of writing to a mass memory 14, means ofreading and of writing from and to a memory 12 and means of access to amodule 13.

The database 11 contains specifications of administration informationbases (MIB standing for Management Information Base or PIB standing forProcess Information Base).

The database 15 contains translation rules for each providing a templatefield type to at least one object specified in the database 11.

The memory 14 is designed to contain templates generated by thetranslator 10.

The memory 12 is designed to contain trees pertaining to MIB or PIBobjects.

The module 13 is designed to perform a typing/naming of objectscommunicated by the translator 10. The module 13 is furnished with aprocessor and with programs required to implement the method stepsdescribed later with reference to FIG. 7.

With reference to FIG. 2, a first step 1 consists in activating in thetranslator 10, a generation of templates for a tree by associatingtherewith a parameter named “ObjectRoot”. The tree can point to a set ofMIBs or of PIBs, to one MIB, a subtree of an MIB or a table of an MIB.The activation may be done on demand or within the framework of theinitialization of the system on the basis of the network 16. Theactivation provides a base for numbering the templates which is aparameter named “base_template_ID”. It will naturally be understood thatthe names given between quotation signs in the description are simplychosen by way of mnemotechnic memorization without any particularsignificance and with no limitative value, that is to say that any othername may be chosen without departing from the framework of theinvention, the names chosen for the description always of coursedesignating the same data as is the case in respect of the references tothe drawings. The activation also provides a parameter pertaining to ageneration of configuration templates, and here named“Generation_templates_configuration”. When the value of this parameteris set for example to 0, this signifies that the method should generateonly standard templates, that is to say those essentially geared towardsmonitoring and signalling. When the value of this parameter is set forexample to 1, this signifies that the method should generate in additionconfiguration templates, that is to say geared essentially towards theconfiguration of the equipment. A standard template pertains to all theobjects and indexes of the tree considered while a configurationtemplate pertains to the indexes, to write-accessible objects and toobject creation.

A second step 2 consists in reading the specifications of the MIBs orPIBs requested, in the memory 11. This memory may be any type of memory(random access memory, disk or network). This step is optional. It isnot necessary if the specifications are already available in thetranslator 10. This step may be repeated during processing if necessary.

A third step 3 consists in constructing a tree for naming the objects onthe basis of the values of the identifiers of objects contained in theMIBs or PIBs.

This step is optional if the tree is already present in the translator10. To construct the objects naming tree, the translator 10 reads thespecifications of the models of data written in the SMI language in theMIBs or PIBs, interprets each clause of the definition of each object soas to place each object in the naming tree using the OIDs of theobjects. It is recalled that an object identifier (OID) is a particulartype of the language ASN.1[X208] using a unique tree defined so as toassociate a portable identifier with a data item. This identifier isabsolute and transferable. The transfer function commonly used isdefined in [X209]. For example SNMP uses the encoding rules of X209.X209 is often named BER (Basic Encoding Rules).

In a fourth step 4, the translator 10 creates templates by executing thesteps described hereinbelow with reference to FIGS. 3 a and 3 b.

A step 39 consists in reading the templates generation request activatedin step 1 in respect of the objects present of the tree of the“ObjectRoot” object and in reading the templates numbering baseparameter “base_template_ID”.

A step 40 consists in creating one or more constants which make itpossible to distinguish families of templates according as a templatepertains to an MIB, a PIB, or to another specification language family.In the example of FIG. 3 a, a constant pertaining to an MIB, is named“DefinitionOf TemplateOf MIB” to which is assigned a value two which iscommon to all MIB templates. Other constants may be allocated with othervalues signifying that the structure constructed in the subsequent stepsis a PIB or other template.

A step 41 consists in creating a “DefTicket_ObjectRoot” template forthis tree. The template is an initially empty list of pairs for exampleof sixteen-bit words.

A step 42 consists in creating a“NumberOftheCurrentField_DefTicket_ObjectRoot” variable and in assigningit a zero value, in creating a “current_template_ID” variable and inassigning it the value of the “base_template_ID” parameter, in creatinga “ObjectRoot_template_ID” variable and in assigning it the value of“current_template_ID”, and finally in incrementing the value of the“current_template_ID” variable. The first variable serves to number thedata fields which will be appended progressively in the subsequent stepsto construct a template. The second variable serves to number thevarious templates which will be created in the subsequent steps so thatthe template of the tree itself is numbered with the third variablewhose value is that of the base parameter provided in step 1. The secondvariable is finally incremented in such a way as to be available with anew value for another template generated in the subsequent steps on thebasis of the objects of the tree.

Following steps 41 and 42 of standard template creation, a step 35consists in testing whether the “Generation_templates_configuration”parameter equals 1. A positive response to the test triggers steps 36and 37 for creating a configuration template in parallel with thestandard template. As we shall see hereinafter, a configuration templaterelates only to modifiable objects from among those of the standardtemplate. The lesser size which results therefrom, reduces theinformation streams necessary during configuration so as to acceleratethe running thereof. The purpose of a standard template is to dispatchthe values of the variables in their existing state, generally doing sofrom the place of measurement to the place of processing. Aconfiguration template for its part, is used to fix values of variables,or even to create new measurements in the measurement system, itsdirection of flow is generally from the place of management to the placeof measurement.

Step 36 of the same nature as step 41, consists in creating aconfiguration template named “DefTicket_configuration_ObjectRoot”.

Step 37, of the same nature as step 42, consists in creating a variablenamed “DefTicket_configuration_ObjectRoot_Template_ID” and in assigningit the value of “current_template_ID” as well as in creating a variablenamed “NumberOfFields_Configuration_ObjectRoot” and in assigning it azero value. The first configuration variable serves to number theconfiguration template directly following the standard template. Thesecond configuration variable serves to count the NumberOfFields of theconfiguration template which is less than or equal to the NumberOfFieldsof the standard template.

Following steps 36 and 37, a step 38 consists in incrementing the“current_template_ID” variable so as to identify a possible subsequentcreation of a template. Step 38 is also activated in case of negativeresponse to the test of step 35 so that the “current_template_ID”variable is incremented independently of the fact that a configurationtemplate is or is not created. Thus, each standard template will have anidentifier of the same nature, for example even, and the correspondingconfiguration template will have a following number identifier, thus ofodd nature which makes it possible on faith to distinguish the nature ofthe template and to match same.

An initially empty standard template and respectively if commanded bystep 1, an initially empty configuration template, that were created bysteps 41 and 42, respectively by steps 36 and 37, the method continuesafter step 38, via a procedure for traversing the tree, describedhereinbelow with reference to FIG. 3 b.

A succession of steps 43 to 47 consists in scanning the tree containedin the memory 12, commencing with the “ObjectRoot” root.

Step 43 consists in initializing a current object to the root object.

Step 44 consists in testing whether the object is an object of scalartype. An MIB contains two categories of objects, the individual objectsalso called scalars and the tables grouping together objects in rows,each row being identified by an index. A positive response to the testof step 44 triggers a scalar procedure. A negative response to the testof step 44 triggers a step 45.

Step 45 consists in testing whether the object is of table type. Apositive response to the test of step 45 triggers a table procedure. Anegative response to the test of step 45 triggers directly step 47described later. The table procedure and the scalar procedure will bedescribed later respectively with reference to FIGS. 4 and 5.

As a preamble to the execution of one of the table or respectivelyscalar procedures, a step 9 consists in extracting table or respectivelyscalar object translation rules, from the rule base 15.

After execution of the table procedure or of the scalar procedure as thecase may be, a step 46 tests whether the current object is the lastobject of the tree. A positive response to the test of step 46 triggersa closure procedure described later with reference to FIG. 6. A negativeresponse to the test of step 46 triggers a step 47. Step 47 takes thenext object of the tree as current object and loops the execution of themethod back to step 44.

After execution of the closure procedure, a step 6 transfers thetemplates generated by the method to respond to a query originating fromthe network 16, directly from another item of equipment or internally.

With reference to FIG. 4 a, the table procedure begins with a step 30 inwhich a variable named “DefTicket_Table_template_ID” is created and towhich is assigned the current value of “current_template_ID”. Thisvariable serves as identifier of a standard template of the tabledetected in step 44.

In a step 31, the value of “current_template_ID” is incremented, so asto be available for a possible subsequent creation of a template.

A step 51 then consists in creating a template of the table, namedDefTicket_Table_Ti. In the same way as the template of the tree createdin step 41, the template of the table created in step 51, is aninitially empty list.

Following steps 30, 31 and 51 of standard template creation, a step 19consists in testing whether the “Generation_templates_configuration”parameter equals 1. A positive response to the test triggers steps 20 to22 for creating a configuration template in parallel with the standardtemplate. As we shall see hereinafter, a configuration template relatesonly to modifiable objects among those of the standard template. Thelesser size which results therefrom reduces the information streamsnecessary during configuration so as to accelerate the running thereof.

Step 20 of the same nature as step 51 consists in creating aconfiguration template named “DefTicket_configuration_Table_Ti”.

Step 21, of the same nature as step 30, consists in creating a variablenamed “DefTicket_configuration_Table_Ti_Template_ID” and in assigning itthe value of “current_template_ID”.

Step 22 consists in creating a variable named“NumberOfFields_Configuration_Table_Ti” and in assigning it a zerovalue.

The variable created and set in step 21, serves to number theconfiguration template directly following the standard template. Thevariable created and set in step 22 serves to count the NumberOfFieldsof the configuration template which is less than or equal to theNumberOfFields of the standard template.

Following steps 20 to 22, a step 23 consists in incrementing the“current_template_ID” variable to identify a possible subsequentcreation of a template. Step 23 is also activated in case of negativeresponse to the test of step 19 so that the “current_template_ID”variable is incremented independently of the fact that a configurationtemplate is or is not created. Thus, each standard template will have anidentifier of the same nature, for example even, and the correspondingconfiguration template will have a following number identifier, thus ofodd nature which makes it possible on faith to distinguish the nature ofthe template and to match same.

A step 52 consists in creating a local variable named“NumberOftheCurrentField_DefTicket_Table_Ti” and in assigning it a zerovalue. Step 52 is executed either following step 51 or following step23, the current field number serving both to index the data fields ofthe standard table template and to compute the quantity thereof.

An initially empty standard template and if commanded by step 1,respectively an initially empty configuration template, that werecreated by steps 30, 51 and 52, respectively by steps 20 to 22, themethod continues with a table traversal procedure, described hereinafterwith reference to FIG. 4 b.

In a step 54, the translator 10 reads the SMI definition of the entryrow of the table and the INDEX clause of the definition.

A loop of steps 55 to 57 consists thereafter in sequentially reading thedefinition SMI of each object of the index. In step 55, the translator10 reads an object of the index beginning with the first objectfollowing the execution of step 54. The translator 10 then triggers thescalar procedure for the object read in step 55 after having triggeredas a preamble step 9 to extract the translation rules if they exist, forthis object from the rule base 15. The step 9 is in fact optional.

Step 56 consists in testing whether the current object is the lastobject of the index. A negative response to the test loops the processback to step 57 for the next object of the index so as to iterativelyrepeat step 55. A positive response to the test of step 56 indicatesthat all the objects of the index have been processed.

After the last execution of step 56, a loop of steps 58 to 61 consistsin processing the objects of the table which are not part of the index.

In step 58, the translator 10 reads a row object beginning with thefirst object of the definition of the table row after the last executionof step 56.

In step 59, the translator 10 tests whether the current object is anobject of the index. A negative response to the test triggers afterexecution of step 9 for the current object, the scalar procedurefollowing which step 60 is activated. A negative response to the test ofstep 59 triggers step 60 directly.

In step 60, the translator 10 tests whether the current object is thelast object of the table. A negative response to the test of step 60triggers step 61 in which the translator 10 reactivates step 58 for thenext object of the table. A positive response to the test of step 60triggers the closure procedure which will be described later withreference to FIG. 6.

The scalar procedure is now described with reference to FIG. 5. In astep 48, a value named “NumberOftheCurrentField” constitutes a callparameter of the scalar procedure. Thus, when the scalar procedure istriggered from step 44, the “NumberOftheCurrentField” variablecorresponds to the “NumberOftheCurrentField_DefTicket_ObjectRoot”variable. When the scalar procedure is triggered from step 55 or step59, the “NumberOftheCurrentField” variable corresponds to the“NumberOftheCurrentField_DefTicket_Table_Ti”. Step 48 increments thevalue of the “NumberOftheCurrentField” variable.

In step 49, the translator 10 reads the SMI definition of the object soas to extract therefrom its type, its subtype, its minimum size, itsmaximum size and its access mode. The access mode makes it possible todistinguish whether the current object is or is not modifiable.

In a step 7, the translator 10 transmits the type of the object, thesubtype of the object, the minimum size of the object, the maximum sizeof the object, the NumberOftheCurrentField and the translation rule forthe current object to the naming typing module 13.

In a step 8, the typing module 13 transmits the values of a pair (type,length) relating to the current object to the translator 10.

In a step 50, the translator 10 appends the pair (type, length) to thetemplate named locally DefTicket_X which is either DefTicket_ObjectRootif the scalar procedure was triggered from step 44, or theDefTicket_Table_Ti template if the scalar procedure was triggered fromstep 55 or step 59.

After execution of step 50, the translator 10 activates a test step 32which consists in verifying whether a configuration template is created,that is to say whether “Generation_templates_configuration”, Gtc forshort, equals 1 and in verifying whether the current object ismodifiable.

A positive response to the test of step 32 triggers a step 33 in which alocally named variable “NumberOfFields_Configuration” is incremented.The “Number of the fields_Configuration” variable corresponds either tothe “NumberOfFields_Configuration_ObjectRoot” variable if the scalarprocedure was triggered from step 44, or to the“NumberOfFields_Configuration_Table_Ti” variable if the scalar procedurewas triggered from step 55 or step 59.

In a step 34, the translator 10 appends the pair (type, length) to thelocally named template DefTicket_Configuration_X which is eitherDefTicket_Configuration_ObjectRoot if the scalar procedure was triggeredfrom step 44, or the DefTicket_Configuration_Table_Ti template if thescalar procedure was triggered from step 55 or step 59. It is seen thatthe pair (type, length) is appended to the configuration template, withthe same tag as in the standard template, namely the current fieldnumber. Thus, each field pertaining to the type and to the length of oneand the same object, is tagged in an identical manner in the standardtemplate and the configuration template, thus facilitating theprocessing of the data by equipment using the method.

After execution of step 34 or following a negative response to the testof step 32, the scalar procedure terminates with a return so as tocontinue the execution of the method at step 46 if the scalar procedurewas triggered from step 44, at step 56 if the scalar procedure wastriggered from step 55 or at step 60 if the scalar procedure wastriggered from step 59.

The closure procedure is described hereinafter with reference to FIG. 6.

In a step 62, the translator 10 inserts a definition of an elementconsisting of a pair (type, length) at the start of the template whoselocal name DefTicket_X corresponds to the name DefTicket_ObjectRoot ifthe procedure is triggered from step 46 and to the nameDefTicket_Table_Ti if the closure procedure is triggered from step 60.

In a step 63, the translator 10 assigns the value of the locally namedvariable “Template_X_ID” to the first term and theNumberOftheCurrentField to the second term of the definition of theelement inserted at step 62. As previously, X is replaced by“ObjectRoot” or “Table_Ti” depending on the call case of the procedure.The type value assigned to the first term constitutes an identifier ofthe template from among the standard templates created. The number ofthe field assigned to the second term, gives a template length,expressed as a quantity of fields each corresponding to a pair (type,length) pertaining to an object processed in the scalar procedure or inthe table procedure as the case may be.

In a step 64, the translator 10 inserts an element definition consistingof a pair (type, length) at the start of the template which results fromstep 62 and whose name DefTicket_X corresponds to the same template nameas in step 62.

In a step 65, the translator 10 assigns the value of the templatedefinition constant of step 40, to the first term of the definition ofthe element inserted at step 64. The value 2 for example, indicates thatthe string of pairs generated, is am MIB template. The translator 10appends 2 to the NumberOftheCurrentField so as to take account of thetwo fields each corresponding respectively to the pair inserted at step62 and to the pair inserted at step 64. When each term of pair isconstituted for example of a two-byte word, the translator 10 multipliesthe result previously obtained by four so as to obtain a template lengthexpressed in bytes which is then assigned to the second term of the pairinserted at step 64.

In a step 5, the translator 10 records the standard template thusobtained in the mass memory 14.

A step 24 consists in testing whether a configuration template creationwas requested, that is to say whether the parameter Gtc for short, isequal to 1. A negative response causes the immediate return of theprocedure, no configuration template needing to be created.

A positive response to the test of step 24 triggers a second test step25 which consists in testing whether the number of configuration fieldsis positive. A negative response to the test causes the return of theprocedure since when no object scanned for the configuration template ismodifiable, the NumberOfFields remains zero and there is then no reasonto record a configuration template.

A positive response to the test of step 25 triggers a string of steps 26to 29 which terminates with step 5 for recording a configurationtemplate before the procedure return, it being noted that there existsat least one field corresponding to a modifiable object.

In step 26, the translator 10 inserts a definition of an elementconsisting of a pair (type, length) at the start of the template whoselocal name DefTicket_Configuration_X corresponds to the nameDefTicket_Configuration_ObjectRoot if the procedure is triggered fromstep 46 and to the name DefTicket_Configuration_Table_Ti if the closureprocedure is triggered from step 60.

In step 27, the translator 10 assigns the value of the locally namedvariable “Template_Configuration_X_ID” to the first term and the currentNumberOfFields to the second term of the definition of the elementinserted at step 26. As previously, X is replaced by “ObjectRoot” or“Table_Ti” depending on the call case of the procedure. The type valueassigned to the first term constitutes an identifier of the templatefrom among the configuration templates created. The NumberOfFields thatis assigned to the second term gives a template length, expressed as aquantity of fields each corresponding to a pair (type, length)pertaining to an object processed in the scalar procedure or in thetable procedure as the case may be.

In step 28, the translator 10 inserts an element definition consistingof a pair (type, length) at the start of the template which results fromstep 27 and whose name DefTicket_Configuration_X corresponds to the sametemplate name as in step 26.

In step 29, the translator 10 assigns the value of the templatedefinition constant of step 40, to the first term of the definition ofthe element inserted at step 64. The value 2 for example, indicates thatthe string of pairs generated, is an MIB template. The translator 10appends 2 to the NumberOftheCurrentField so as to take account of thetwo fields each corresponding respectively to the pair inserted at step26 and to the pair inserted at step 28. When each term of pair isconstituted for example of a two-byte word, the translator 10 multipliesthe result previously obtained by four so as to obtain a template lengthexpressed in bytes which is then assigned to the second term of the pairinserted at step 64.

In step 5, the translator 10 records the configuration template thusobtained in the mass memory 14.

The naming typing module 13 executes the method described hereinafterwith reference to FIG. 7.

In a step 70, the module 13 receives the OID of the object, the type ofthe object, the subtype of the object, the minimum size of the object,the maximum size of the object, the NumberOftheCurrentField and thetranslation rule which were transmitted to it by the translator 10 instep 7 of the scalar procedure.

In a step 71, the module 13 creates a variable named“Type_field_template” and assigns it the NumberOftheCurrentFieldreceived at step 70. This step allows the module 13 to transmit adefault type which is the current field number in the standard template.

In a step 72, the module 13 creates a variable namedlength_field_template and assigns it the maximum size of the objectreceived at step 70. This step allows the module 13 to transmit adefault length which is the maximum length that a field can have for thecurrent object.

In a step 73, the module 13 tests whether there exists an SMI subtypefor the current object. A positive response to the test triggers a step74 and a negative response to the test triggers a step 75.

In step 74, the module 13 determines the maximum length of the SMIsubtype and assigns this length to the length_field_template variable.

Step 75 consists in testing whether a translation rule associates atemplate field type with the object corresponding to the OID received orits SMI type or its SMI subtype. A positive response to the testtriggers a step 76. A negative response to the test triggers a step 78.

In step 76, the module 13 then assigns the field type afforded by therule, to the “type_field_template” variable.

In a step 77, the module 13 assigns the length of this field type, tothe variable named “length_field_template”. Moreover, if there exists atranslation rule associating a length restriction with the objectcorresponding to the OID received, then this length is assigned to the“length_field_template” variable.

In step 78, the module 13 transmits a pair (type, length) whose firstvalue is that of the “type_field_template” variable and whose secondvalue is that of the “length_field_template” variable to the translator10.

The method in action will now be described on the basis of an exemplaryobject which is a known table “bufferControlTable” with reference toFIGS. 8 to 10 and of an exemplary object which is another known table“Aa15VccTable” with reference to FIGS. 11 to 13.

FIG. 8 is a tree representation for an MIB table whose annexe 1 gives anSMI definition extract that can be found in greater detail on pages 75to 77 of RFC2819 available at the internet site http://www.ietf.org.

The first column on the left of the array gives a node number (OID forObject Identifier) referencing an object named in the second column withits type in the third column and its length in the fourth column. Thelast column on the right gives a length of subtype if one exists. Thestring of first figures of the node number 1.3.6.1.2.16 gives thelocation of an MIB 11 in the tree arrangement of MIBs. The next figure8.1. indicates the location of the “BufferControlTable” object in thisMIB. The tree arrangement of the objects of the table is given by thefigures 1.1 to 1.13.

The tree or subtree represented in FIG. 8 is an example of content ofthe memory 12, obtained by the translator 10 on the basis of the SMIdefinition of annexe 1.

FIG. 9 shows an exemplary standard template the generation of which bythe method is described hereinafter.

When the translator 10 traverses the tree of the MIB 11 referenced1.3.6.1.2.1.16.8 in memory 12, it encounters at step 44, the“bufferControlTable” object which is a table referenced1.3.6.1.2.1.16.8.1 in memory 12. The translator 10 then executes thetable procedure for which we assume for example that the“current_template_ID” variable equals 302 at this moment in step 30.

In step 31, the “current_template_ID” variable is set to 303. In step51, the translator 10 creates the template of FIG. 9, initially empty.It is assumed that in step 19, “Generation_templates_configuration”equals zero for simplicity. In step 23, the “current_template_ID”variable then equals 304. In step 52, the“NumberOftheCurrentField_DefTicket_Table_Ti” variable equals zero.

In step 55, the translator 10 encounters the “bufferControlIndex” objectfor which it executes the scalar procedure.

In step 48, the “NumberOftheCurrentField_DefTicket_Table_Ti” variableequals 1.

In step 49, the SMI definition of the object gives the type Integer32with a subtype of maximum size of 2. In step 8, the typing modulereturns a pair of value (1,2). In step 50, the translator 10 appends thepair (1,2) in the form of two binary numbers 121 each of two bytes tothe template of FIG. 9.

Following steps 56 and 57, in step 55, the translator 10 encounters the“bufferControlChannelIndex” object for which it executes the scalarprocedure.

In step 48, the “NumberOftheCurrentField_DefTicket_Table_Ti” variableequals 2.

In step 49, the SMI definition of the object gives the type Integer32with a subtype of maximum size of 2. In step 8, the typing modulereturns a pair of value (2,2). In step 50, the translator 10 appends thepair (2,2) in the form of two binary numbers 122 each of two bytes tothe template of FIG. 9.

Following step 56, the translator 10 again encounters the two previousobjects and goes directly to the next object in step 61.

In step 58, the translator 10 encounters the “bufferControlFullStatus”object for which it executes the scalar procedure.

In step 48, the “NumberOftheCurrentField_DefTicket_Table_Ti” variableequals 3.

In step 49, the SMI definition of the object gives the type INTEGER witha subtype of size 2. In step 8, the typing module returns a pair ofvalue (3,2). In step 50, the translator 10 appends the pair (3,2) in theform of two binary words 123 each of two bytes to the template of FIG.9.

The above explanations can be repeated for each subsequent object of thearray of FIG. 8, the translator 10 then appending in step 50, for eachencountered in step 58, respectively the pair (4,2), (5,2), (6,2),(7,4), (8,4), (9,4), (10,4), (11,4), (12,32), (13,4) in the respectiveform of two binary words 124, 125, 126, 127, 128, 129, 130, 131, 132,133 each of two bytes to the template of FIG. 9.

After reaching the “bufferControlStatus” object in step 60, the templateof FIG. 9 is then constituted of a string of pairs of words 121 to 133.The translator 10 executes the closure procedure.

In step 62, the translator 10 appends a pair of binary words 120 to thestart of the template. In step 63, the translator 10 assigns the value302 to the first word and the value 13 to the second word of the pair.

In step 64, the translator 10 appends a pair of binary words 119 to thestart of the template. In step 65, the translator 10 assigns the value 2to the first word and the value 60 to the second word of the pair.

In step 5, the translator 10 records the template such as it ultimatelyappears in FIG. 9.

The template of FIG. 9 makes it possible to transmit data tickets whosevalues are contained in rows of the “bufferControlTable” table.

FIG. 10 shows an exemplary data ticket. Let us assume that row 34 of thetable gives the following values:

bufferControlIndex = 34 bufferControlChannelIndex = 654bufferControlFullStatus = 2 bufferControlFullAction = 542bufferControlCaptureSliceSize = 512 bufferControlDownloadSliceSize = 200bufferControlDownloadOffset = 32 bufferControlMaxOctetsRequested =100000000 bufferControlMaxOctetsGranted = 1000000bufferControlCapturedPackets = 10000 bufferControlTurnOnTime =3454764364 bufferControlOwner = acme bufferControlStatus = 3

In the corresponding data ticket of FIG. 10, a two-byte word 99 containsthe value 302 which references the template of FIG. 9. A two-byte word100 contains the value 72 which represents the aggregate length of the13 data fields indicated by the template of FIG. 9 with the two words 99and 100, i.e. the total length of the data ticket.

Thereafter fields 101 to 106 the length of each of which is givenrespectively by the second word of the pairs 121 to 126 of the template,contain respectively the values 34, 654, 2, 542, 512 and 200. Fields 107to 111 the length of each of which is given respectively by the secondword of the pairs 127 to 131 of the template, contain the values 32,100000000, 1000000 and 3454764364. A field 112 the length of which isgiven by the second word of the pair 132 contains the character stringacme for example coded in ASCII. A field 113 the length of which isgiven by the second word of the pair 133 contains the value 3.

For each field value of the data ticket, the type given by the firstword of each of the pairs 121 to 133 of the template allows a recipientof the ticket to recognize which object this value belongs to.

The economy of bandwidth and the simplification of calculation madepossible by the use of the data tickets will be noted. The SNMP messageheader data are ignored. The data ticket of FIG. 10 contains only fourheader bytes, the first two for referencing the corresponding templateand the last two for indicating the length thereof so as to transmit thecontent of a table row previously obtained by an SNMP Get.

To obtain the same row by SNMP, an interrogation query followed by aresponse query would have been necessary first. The interrogation querywould have required a trio (object identifier+index value, length,value) per object where “object identifier” is the OID of a table field,index value is the value of the BufferControlIndex index for identifyingmore precisely an instance of the object, that is to say 12*(11+2) bytesi.e. 156 bytes. The response would have required the 30 bytes of valuesin addition, i.e. 186 bytes.

By comparison of the 72 bytes of the data ticket, SNMP is therefore muchmore greedy in terms of messages and especially in terms of byte ratesince it generates four times as much traffic. It is true that thetransfer of data by ticket requires prior transmission of a templatewhich in the previously described example of FIG. 9, represents 60bytes, cutting the generation of traffic to just a half for atransmission of first ticket by comparison with SNMP. However, one andthe same template may be used for successive tickets without needing tobe transmitted again, thus reducing the traffic in a proportion of 2 to4.

FIG. 11 is a tree representation for a table of the MIB ATM whose annexe2 gives an SMI definition extract that can be found in greater detail onpages 61 to 63 of RFC1695 available at the internet sitehttp://www.ietf.org.

The first column on the left of the array gives a node numberreferencing an object named in the second column with its type in thethird column and its length in the fourth column. The last column givesthe length of the subtype, if it exists. The node number in the generaltree arrangement of the MIBs, is also called the OID (ObjectIdentifier). The string of first figures of the node number1.3.6.1.2.1.37 gives the location of the MIB ATM in the tree arrangementof the MIBs. The following figure 1.12 indicates the location of the“aal5VccTable” object in the MIB ATM. A tree arrangement of objects ofthe table is given by the figures 1.1 to 1.5.

In the SMI specification of annexe 2, the index of the table isconstituted by three objects “if Index”, aal5VccVpi” and “aal5VccVci”.The last two objects belonging to the table considered. The first objectbelongs to the “if Table” table of another MIB pertaining to thephysical interfaces, known by the name of MIBII and located in the treearrangement of the MIBs by the figures 1.3.6.1.2.1. The figure 2.2locates the table in the MIBII the “ifIndex” object for its part islocated by the figures 1.1. in the tree arrangement of the “ifTable”table.

On the basis of the SMI definition of Annexe 2 and of the MIB II in step3, the translator 10 constructs a naming tree in memory 5. This tree isdefined on the basis of the figures of the OIDs of FIG. 11.

FIG. 12 shows an exemplary standard template whose generation by themethod is described hereinafter.

When the translator 10 traverses the subtree 1.3.6.1.2.1.37 of the treeconsisting of the MIB II and of the MIB ATM in memory 12, it encountersin step 44, the “aal5VccTable” object which is a table referenced1.3.6.1.2.1.37.1.12 in memory 12. The translator 10 then executes thetable procedure for which we assume for example that the“current_template_ID” variable equals 303 at this moment in step 30.

In step 31, the “current_template_ID” variable is set to 304. In step51, the translator 10 creates the template of FIG. 12, initially empty.It is assumed that in step 19, “Generation_templates_configuration”equals zero for simplicity. In step 23, the “current_template_ID”variable then equals 305. In step 52, the“NumberOftheCurrentField_DefTicket_Table_Ti” variable equals zero.

In step 55, the translator 10 encounters the “ifindex” index, first termof the index, for which it executes the scalar procedure.

In step 48, the “NumberOftheCurrentField_DefTicket_Table_Ti” variableequals 1.

In step 49, the SMI definition of the object gives the type INTEGER witha maximum size of 4. In step 8, the typing module returns a pair ofvalue (1,4). In step 50, the translator 10 appends the pair (1,4) in theform of two binary words 81 each of two bytes to the template of FIG.12.

Following steps 56 and 57, in step 55, the translator 10 encounters the“aal5VccVpi” object, second term of the index, for which it executes thescalar procedure.

In step 48, the “NumberOftheCurrentField_DefTicket_Table_Ti” variableequals 2.

In step 49, the SMI definition of the object gives the typeAtmVpIdentifier with a subtype of maximum size 2. In step 8, the typingmodule returns a pair of value (2,2). In step 50, the translator 10appends the pair (2,2) in the form of two binary words 82 each of twobytes to the template of FIG. 12.

Following steps 56 and 57, in step 55, the translator 10 encounters thethird term of the index, the “aa15VccVci” object for which it executesthe scalar procedure.

In step 48, the “NumberOftheCurrentField_DefTicket_Table_Ti” equals 3.

In step 49, the SMI definition of the object gives the typeAtmVcIdentifier with a subtype of maximum size 2. In step 8, the typingmodule returns a pair of value (3,2). In step 50, the translator 10appends the pair (3,2) in the form of two binary words 83 each of twobytes to the template of FIG. 12.

Following step 56, the translator 10 again encounters the three previousobjects and goes each time directly to the next object in step 61passing through steps 58, 59, 60 and 61.

In step 58, the translator 10 encounters the “aa15VccCrcErrors” objectfor which it executes the scalar procedure.

In step 48, the “NumberOftheCurrentField_DefTicket_Table_Ti” variableequals 4.

In step 49, the SMI definition of the object gives the type Counter32with a maximum size of 4. In step 8, the typing module returns a pair ofvalue (4,4). In step 50, the translator 10 appends the pair (4,4) in theform of two binary words 84 each of two bytes to the template of FIG.12.

The above explanations may be repeated for each subsequent object of thearray of FIG. 11, the translator 10 then appending in step 50, for eachone encountered in step 58, respectively the pair (5,4), (6,4), in therespective form of two binary words 85, 86, each of two bytes to thetemplate of FIG. 12.

After reaching the “aal5VccOverSizedSDUs” object in step 60, thetemplate of FIG. 12 is then constituted by a series of pairs of words 81to 86, the translator 10 executes the closure procedure.

In step 62, the translator 10 appends a pair of binary words 80 to thestart of the template. In step 63, the translator 10 assigns the value303 to the first word and the value 6 to the second word of the pair.

In step 64, the translator 10 appends a pair of binary words 79 to thestart of the template. In step 65, the translator 10 assigns the value 2to the first word and the value 32 to the second word of the pair.

In step 5, the translator 10 records the template such as it finallyappears in FIG. 12.

The template of FIG. 12 makes it possible to transmit data tickets whosevalues are contained in rows of the “aa15VccTable”. The tickets aregenerally grouped together in blocks of tickets intended to be sent to acollector.

FIG. 13 shows an exemplary data ticket. Let us assume that the row ofthe table describing the quality of the traffic of the ATM circuittravelling through the interface 12 and identified as the virtualcircuit corresponding to the Vci 1000 of the Vpi 100, gives thefollowing values:

ifIndex = 12 aal5VccVpi 100 aal5VccVci = 1000 aal5VccCrcErrors = 15432aal5VccSarTimeOuts = 456 aal5VccOverSizedSDUs = 567.

In the corresponding data ticket of FIG. 13, a two-byte word 199contains the value 303 which references the template of FIG. 12. Atwo-byte word 200 contains the value 24 which represents the aggregatelength of the six data fields indicated by the template of FIG. 9 withthe two words 199 and 200, i.e. the total length of the data ticket.

Subsequently fields 201 to 206 the length of each of which is givenrespectively by the second word of the pairs 81 to 86 of the template,contain respectively the values 12, 100, 1000, 15432, 456 and 567.

For each field value of the data ticket, the type given by the firstword of each of the pairs 81 to 86 of the template, allows a recipientof the ticket to recognize which object this value belongs to.

Here again will be noted the economy of bandwidth and the simplificationof calculation that is made possible by the use of the data tickets.

With reference to FIG. 14, a measurement system 91 comprises probes 89for measuring performance of IP networks and a system controller 90 towhich the probes 89 are connected.

An SNMP agent 93 implements the MIB 11 IPPM REPORTING MIB in proxy mode.It is defined in www.ietf.org/html.characters/ippm-character.html. Theagent 93 is hosted in a proxy server 92 so as to provide a standardmanagement interface for the measurement system 91, to networkmanagement systems 94 (NMS standing for Network Management Station)which can then consult the measurements in progress and their resultsusing the SNMP conventional protocol.

It is understood that the known management interface IPPM REPORTING MIBdefines several tables whose ippmNetworkMeasureTable andippmHistoryTable tables are adopted here by way of example to illustratean industrial use of the method which is the subject of the invention.The network measurement table 95 named ippmNetworkTable carriesdefinitions of measurements set in place between the probes by asupervisor 87 hosted in the controller 90. The supervisor 87 performsthe collection of the results of the measurements originating from theprobes 89. The history table 96 named ippmHistoryTable stores theresults of the measurements received from the supervisor. The agent 93comprises a copy of these two tables among others.

So as to be able to use the method described previously, the system 90is in accordance with the representation of FIG. 1. Found again in FIG.14 is the translator 10 and the MIB specification 11. Here, the functionof the translator 10 among other things is to generate templates for theippmNetworkTable and ippmHistoryTable tables.

The system 91 also comprises a module 88 for exporting templates anddata tickets. The proxy server 92 comprises a module 18 for receivingtemplates and data tickets. To communicate, the modules 18 and 88 use aprotocol named IPFIX, specially adapted for the exchanges of templatesand of tickets between modules.

The proxy server 92 also comprises or has access to an instance of thetranslator 10 and of the MIB 11. Thus when the system 91 despatches atemplate to the proxy server 92 by means of the module 88, the proxyserver 92 receiving this template by means of the module 18, can prepareitself to receive data tickets containing the descriptions and theresults of measurements issued following the template by the system 91.The proxy server 92 comprises a module 17 which is enabled by thetranslator 10 to match up the fields of the template with the SMIdefinitions of objects so as to supply the agent 93 with tables and withobjects in agreement with the values which will be received in the datatickets.

Subsequently, the measurement system 91 uses the IPFX protocol tohandover with the flow the measurements put in place and the results ofthese measurements, to the proxy server 92. The station 94 can thenreceive the measurements of the agent 93 in a conventional manner viathe SNMP protocol.

FIG. 15 gives an exemplary template of the ippmHistoryTable tableobtained in the system 91 by means of the method described previously.Here the values in the various fields are expressed in decimals so as tofacilitate fast reading thereof, given that in reality they areexpressed in binary form.

The first and the second word of the pair 139 contain respectively thevalue 2 to indicate that the data structure is a template and the value36 indicating in bytes the length of the template.

The first and the second word of the pair 140 contain respectively thevalue 304 to indicate that the template pertains to the history tableand the value 7 indicating the quantity of data fields of the template.

The first and the second word of the pair 141 pertaining to the“ippmHistoryMeasureOwner” object, contain respectively the value 1 toindicate the field type and the value 32 indicating in bytes the lengthof the field.

The first and the second word of the pair 142 pertaining to the“ippmHistoryMeasureIndex” object, contain respectively the value 2 toindicate the field type and the value 4 indicating in bytes the lengthof the field.

The first and the second word of the pair 143 pertaining to the“ippmHistoryMetricIndex” object, contain respectively the value 3 toindicate the field type and the value 4 indicating in bytes the lengthof the field.

The first and the second word of the pair 144 pertaining to the“ippmHistoryIndex” object, contain respectively the value 4 to indicatethe field type and the value 4 indicating in bytes the length of thefield.

The first and the second word of the pair 145 pertaining to the“ippmHistorySequence” object, contain respectively the value 5 toindicate the field type and the value 4 indicating in bytes the lengthof the field.

The first and the second word of the pair 146 pertaining to the“ippmHistoryTimestamp” object, contain respectively the value 6 toindicate the field type and the value 8 indicating in bytes the lengthof the field.

The first and the second word of the pair 147 pertaining to the“ippmHistoryValue” object, contain respectively the value 7 to indicatethe field type and the value 4 indicating in bytes the length of thefield.

FIG. 16 gives an exemplary data ticket of the ippmHistoryTable tableobtained in the system 91 so as to be readable by means of the templateof FIG. 15. As is the case for the other template or data ticketdrawings, a line width represents four bytes, a line height is nothowever proportional to the number of bytes for a field of more thaneight bytes so that the representation of the drawing can be kept to areasonable number of pages.

The first field 149 contains on two bytes, the value 304 which is thatof the first word of the pair 140 in the corresponding template.

The second field 150 contains on two bytes the value 64 to indicate thequantity of bytes of the data ticket.

The field 151 pertaining to the “ippmHistoryMeasureOwner” object,contains the character string FTRD coded in binary.

The field 152 pertaining to the “ippmHistoryMeasureIndex” object,contains the value 5 which indexes the measurement and the value 6 whichindexes a simple outward delay.

The field 153 pertaining to the “ippmHistoryMetricIndex” object,contains the value 6 which indexes the type of metric measured, on thisoccasion 6 corresponds to a unidirectional delay.

The field 154 pertaining to the “ippmHistoryIndex” object, contains thevalue 123 to indicate that the result of the measurement transmitted inthis ticket, is the 123^(rd).

The field 155 pertaining to the “ippmHistorySequence” object, containsthe value 1057582058 to indicate that the measurement was taken on 14Oct. 2002 at 9 hours 54 minutes 18 seconds.

The field 156 pertaining to the “ippmHistoryTimestamp” object, containsthe value 4578845678 representative of a time stamping fractional share.

The field 157 pertaining to the “ippmHistoryValue” object, contains thevalue 567 which is that of the delay measurement, the unit being givenby the field 152.

FIG. 17 gives an exemplary template of the ippmNetworkTable tableobtained in the system 91 by means of the method described previously.Here again the values in the various fields are expressed in decimals soas to facilitate fast reading thereof, given that in reality they areexpressed in binary form.

The first and the second word of the pair 159 contain respectively thevalue 2 to indicate that the data structure is an MIB template and thevalue 116 indicating in bytes the length of the template.

The first and the second word of the pair 160 contain respectively thevalue 302 to indicate that the template pertains to the table of networkmeasurements and the value 27 indicating the quantity of data fieldsformatted by the template.

The first and the second word of the pair 161 pertaining to the“ippmNetworkMeasureOwner” object, contain respectively the value 1 toindicate the field type and the value 32 indicating in bytes the lengthof the field.

The first and the second word of the pair 162 pertaining to the“ippmNetworkMeasureIndex” object, contain respectively the value 2 toindicate the field type and the value 2 indicating in bytes the lengthof the field.

The first and the second word of the pair 163 pertaining to the“ippmNetworkMetricName” object, contain respectively the value 3 toindicate the field type and the value 256 indicating in bytes the lengthof the field.

The first and the second word of the pair 164 pertaining to the“ippmNetworkMeasureMetrics” object, contain respectively the value 4 toindicate the field type and the value 8 indicating in bytes the lengthof the field.

The first and the second word of the pair 165 pertaining to the“ippmNetworkMeasureBeginTime” object, contain respectively the value 5to indicate the field type and the value 4 indicating in bytes thelength of the field.

The first and the second word of the pair 166 pertaining to the“ippmNetworkMeasureCollectionRateUnit” object, contain respectively thevalue 6 to indicate the field type and the value 4 indicating in bytesthe length of the field.

The first and the second word of the pair 167 pertaining to the“ippmNetworkMeasureCollectionRate” object, contain respectively thevalue 7 to indicate the field type and the value 4 indicating in bytesthe length of the field.

The first and the second word of the pair 168 pertaining to the“ippmNetworkMeasureDurationUnit” object, contain respectively the value8 to indicate the field type and the value 4 indicating in bytes thelength of the field.

The first and the second word of the pair 169 pertaining to the“ippmNetworkMeasureDuration” object, contain respectively the value 9 toindicate the field type and the value 4 indicating in bytes the lengthof the field.

The first and the second word of the pair 170 pertaining to the“ippmNetworkMeasureHistorySize” object, contain respectively the value10 to indicate the field type and the value 4 indicating in bytes thelength of the field.

The first and the second word of the pair 171 pertaining to the“ippmNetworkMeasureFailureMgmtMode” object, contain respectively thevalue 11 to indicate the field type and the value 4 indicating in bytesthe length of the field.

The first and the second word of the pair 172 pertaining to the“ippmNetworkMeasureResultsMgmt” object, contain respectively the value12 to indicate the field type and the value 4 indicating in bytes thelength of the field.

The first and the second word of the pair 173 pertaining to the“ippmNetworkMeasureScrcTypeP” object, contain respectively the value 13to indicate the field type and the value 512 indicating in bytes thelength of the field.

The first and the second word of the pair 174 pertaining to the“ippmNetworkMeasureScrc” object, contain respectively the value 14 toindicate the field type and the value 512 indicating in bytes the lengthof the field.

The first and the second word of the pair 175 pertaining to the“ippmNetworkMeasureDstTypeP” object, contain respectively the value 15to indicate the field type and the value 512 indicating in bytes thelength of the field.

The first and the second word of the pair 176 pertaining to the“ippmNetworkMeasureDst” object, contain respectively the value 16 toindicate the field type and the value 512 indicating in bytes the lengthof the field.

The first and the second word of the pair 177 pertaining to the“ippmNetworkMeasureTransmitMode” object, contain respectively the value17 to indicate the field type and the value 4 indicating in bytes thelength of the field.

The first and the second word of the pair 178 pertaining to the“ippmNetworkMeasureTransmitPacketRateUnit” object, contain respectivelythe value 18 to indicate the field type and the value 4 indicating inbytes the length of the field.

The first and the second word of the pair 179 pertaining to the“ippmNetworkMeasureTransmitPacketRate” object, contain respectively thevalue 19 to indicate the field type and the value 4 indicating in bytesthe length of the field.

The first and the second word of the pair 180 pertaining to the“ippmNetworkMeasureDeviationOrBurstsize” object, contain respectivelythe value 20 to indicate the field type and the value 4 indicating inbytes the length of the field.

The first and the second word of the pair 181 pertaining to the“ippmNetworkMeasureMedianOrInterBurstsize” object, contain respectivelythe value 21 to indicate the field type and the value 4 indicating inbytes the length of the field.

The first and the second word of the pair 182 pertaining to the“ippmNetworkMeasureLossTimeout” object, contain respectively the value22 to indicate the field type and the value 4 indicating in bytes thelength of the field.

The first and the second word of the pair 183 pertaining to the“ippmNetworkMeasureL3PacketSize” object, contain respectively the value23 to indicate the field type and the value 4 indicating in bytes thelength of the field.

The first and the second word of the pair 184 pertaining to the“ippmNetworkMeasureDataPattern” object, contain respectively the value24 to indicate the field type and the value 4 indicating in bytes thelength of the field.

The first and the second word of the pair 185 pertaining to the“ippmNetworkMeasureMap” object, contain respectively the value 25 toindicate the field type and the value 256 indicating in bytes the lengthof the field.

The first and the second word of the pair 186 pertaining to the“ippmNetworkMeasureSingletons” object, contain respectively the value 26to indicate the field type and the value 4 indicating in bytes thelength of the field.

The first and the second word of the pair 187 pertaining to the“ippmNetworkMeasureoperState” object, contain respectively the value 27to indicate the field type and the value 4 indicating in bytes thelength of the field.

FIG. 18 gives an exemplary data ticket of the ippmNetworkTable tableobtained in the system 91 so as to be readable by means of the templateof FIG. 17.

The first field 259 contains the value 302 which is that of the firstword of the pair 159 in the corresponding template.

The second field 260 contains the value 2676 to indicate the ticketlength expressed in bytes.

The field 261 pertaining to the “ippmNetworkMeasureOwner” object,contains the character string FTRD coded in binary to indicate theproprietor of the measurement.

The field 262 pertaining to the “ippmNetworkMeasureIndex” object,contains the value 5 to indicate the measurement number.

The field 263 pertaining to the “ippmNetworkMetricName” object, containsthe character string “One-way-delay between Paris and Lannion” coded inbinary to indicate in plain text what the measurement refers to.

The field 264 pertaining to the “ippmNetworkMeasureMetrics” object,contains the value 6 to indicate the type of measurement.

The field 265 pertaining to the “ippmNetworkMeasureBeginTime” object,contains the value 1034582058 to indicate that the measurement startedon 14 Sep. 2003 at 9 hours 54 minutes 18 seconds.

The field 266 pertaining to the “ippmNetworkMeasureCollectionRateUnit”object, contains the value 0 representative of a time stampingfractional share.

The field 267 pertaining to the “ippmNetworkMeasureCollectionRate”object, contains the value 10 to indicate the sampling rate.

The field 268 pertaining to the “ippmNetworkMeasureDurationUnit” object,contains the value 6 to indicate that the unit of duration of themeasurement is a second.

The field 269 pertaining to the “ippmNetworkMeasureDuration” object,contains the value 120 to indicate that the measurement lasted 120seconds.

The field 270 pertaining to the “ippmNetworkMeasureHistorySize” object,contains the value 1000 to indicate the size of the measurement history.

The field 271 pertaining to the “ippmNetworkMeasureFailureMgmtMode”object, contains the value 1 to indicate the automatic mode.

The field 272 pertaining to the “ippmNetworkMeasureResultsMgmt” object,contains the value 1 to indicate that the results are communicated withautomatic looping.

The field 273 pertaining to the “ippmNetworkMeasureScrcTypeP” object,contains the character string “IP UDP” to indicate the transfer protocolused by the communication on departure from Paris which forms thesubject of the measurement.

The field 274 pertaining to the “ippmNetworkMeasureScrc” object,contains the value 80.168.0.1 3456 to indicate the source address of thecommunication, here Paris.

The field 275 pertaining to the “ippmNetworkMeasureDstTypeP” object,contains the character string “IP UDP” to indicate the transfer protocolused by the communication destined for Lannion which forms the subjectof the measurement.

The field 276 pertaining to the “ippmNetworkMeasureDst” object, containsthe value 180.168.0.1 6543 to indicate the destination address of thecommunication, here Lannion.

The field 277 pertaining to the “ippmNetworkMeasureTransmitMode” object,contains the value 1 to indicate that the mode of transmission isperiodic.

The field 278 pertaining to the“ippmNetworkMeasureTransmitPacketRateUnit” object, contains the value 6to indicate that the packet rate unit of 64 bytes transmitted, is persecond.

The field 279 pertaining to the “ippmNetworkMeasureTransmitPacketRate”object, contains the value 100 to indicate that the sending rate was 100packets per second.

The field 280 pertaining to the “ippmNetworkMeasureDeviationOrBurstsize”object, contains the value of 0 to indicate a zero deviation.

The field 281 pertaining to the“ippmNetworkMeasureMedianOrInterBurstsize” object, contains the value 0to indicate a zero burst size.

The field 282 pertaining to the “ippmNetworkMeasureLossTimeout” object,contains the value 15 to indicate that the delay on expiry of which apacket is considered to be lost, is 15 seconds.

The field 283 pertaining to the “ippmNetworkMeasureL3PacketSize” object,contains the value 64 to indicate that the size of the packets sent inthe communication which forms the subject of the measurement, is 64bytes.

The field 284 pertaining to the “ippmNetworkMeasureDataPattern” object,contains the value FFFF to indicate the format of the measurement data.

The field 285 pertaining to the “ippmNetworkMeasureMap” object, containsthe character string “internal network” to indicate in plain text thetype of network.

The field 286 pertaining to the “ippmNetworkMeasureSingletons” object,contains the value 0 by default.

The field 287 pertaining to the “ippmNetworkMeasureOperState” object,contains the value 0 by default.

The person skilled in the art will readily appreciate the economy ofbandwidth necessary for the transferring of the measurements between thesystem 91 and the server 92, on the basis of the two examples of datatickets which have just been described, by comparison with that whichwould have been necessary using the SNMP protocol at this level.

The method implemented in the system described, according to theinvention, is especially useful since it makes it possible toautomatically generate templates on the basis of MIBs or PIBs for anytype of data structure, relieving the human being of irksome tasks whichin the absence of the invention, would have consisted in manuallydefining a template for each particular data structure, the quantity ofpossible data structures in this field being considerable.

Annex 1

bufferControlTable OBJECT-TYPE SYNTAX SEQUENCE OF { bufferControlIndexInteger32, bufferControlChannelIndex Integer32, bufferControlFullStatusINTEGER, bufferControlFullAction INTEGER, bufferControlCaptureSliceSizeInteger32, bufferControlDownloadSliceSize Integer32,bufferControlDownloadOffset Integer32, bufferControlMaxOctetsRequestedInteger32, bufferControlMaxOctetsGranted Integer32,bufferControlCapturedPackets Integer32, bufferControlTurnOnTimeTimeTicks, bufferControlOwner OwnerString, bufferControlStatusEntryStatus } INDEX {bufferControlIndex} ::={capture 1}

Annex 2

aal5VccTable OBJECT-TYPE SYNTAX SEQUENCE OF { aal5VccVpi INTEGER,aal5VccVci INTEGER, aal5VccCrcErrors Counter32, aal5VccSarTimeOutsCounter32, aal5VccOverSizedSDUs Counter32 } INDEX {ifIndex, aal5VccVpi,aal5VccVci} ::= {atmMIBObjects 1}

1. A method for minimizing a bandwidth required for a transfer ofcommunication network administration information, said informationrelating to objects pertaining to hardware, software or networkoperation elements, catalogued in an administration information base andwith each of which is associated a formal language specification,comprising the steps of: generating on a basis of a formal languagespecification for each object, a pair of words for which a value offirst word pertains to an indication of the object and a value of secondword pertains to an information length of the object; constructing atemplate comprising an ordered set of pairs of words generated and anidentifier of said template, said template indicating an ordered stringof information to be sent; exporting said template; and progressivelyexporting the ordered string of information corresponding to saidtemplate, said ordered string of information corresponding to saidcommunication network administration information relating to saidobject.
 2. The method as claimed in claim 1, further comprising thesteps of: traversing a tree of the administration information base eachnode of which is associated with an object; testing at each node whetherthe object is of scalar or table type; constructing the template byappending the word pair generated to the template if the object is ofscalar type; constructing template if the object is of table type forthe objects of the table.
 3. The method as claimed in claim 1, furthercomprising the step of constructing a configuration template comprisingthe pairs of words generated for objects with modifiable access.
 4. Amethod of transmitting communication network administration information,said information relating to objects pertaining to hardware, software ornetwork operation elements, catalogued in an administration informationbase and with each of which is associated a formal languagespecification, comprising the steps of: obtaining a template comprisingan identifier of said template and an ordered set of pairs of words,each pair of words being generated for one of said objects on a basis ofa formal language specification associated with said object andcomprising a first word having a value pertaining to an indication ofsaid object and a second word having a value pertaining to aninformation length of said object; exporting said template; andprogressively exporting an ordered string of information correspondingto said template, said ordered string of information corresponding tosaid communication network administration information relating to saidobject.
 5. A system for minimizing a bandwidth required for a transferof communication network administration information, said informationrelating to objects pertaining to hardware, software or networkoperation elements, catalogued in an administration information base andwith each of which is associated a formal language specification, saidsystem comprising: a translator machine configured: to generate on abasis of a formal language specification for each object, a pair ofwords a value of whose first word pertains to an indication of theobject and a value of whose second word pertains to an informationlength of the object; to generate a template comprising an ordered setof pairs of words and an identifier, said template indicating an orderedstring of information to be sent; to export said template; and toprogressively export the ordered string of information corresponding tosaid template, said ordered string of information corresponding to saidcommunication network administration information relating to saidobject.
 6. The system as claimed in claim 5, wherein the translatormodule is designed to traverse a tree of the administration informationbase each node of which is associated with an object, to test at eachnode whether the object is of scalar or table type and to construct thetemplate by appending the word pair generated to the template if theobject is of scalar type or construct another so-called table templateif the object is of table type for the objects of the table.
 7. Thesystem as claimed in claim 5 wherein the translator module is designedto construct in addition a configuration template comprising the pairsof words generated for objects with modifiable access.
 8. The system asclaimed in claim 5, further comprising a supervisor module designed tocollect measurements and an exportation module designed to transmit atleast one ticket of data pertaining to these measurements to a server.9. The system as claimed in claim 8, wherein said exportation module isdesigned to transmit: a data ticket comprising a reference to atemplate, preceded, in the transmission, by the template referenced insaid data ticket.
 10. A computer-readable memory having stored thereon aprogram executable by a processor for performing a method, the programincluding: an exportation module for a system for minimizing a bandwidthrequired for a transfer of communication network administrationinformation, said information relating to objects pertaining tohardware, software or network operation elements, catalogued in anadministration information base and with each of which is associated aformal language specification; program codes for generating a templatecomprising: an ordered set of pairs of words; and an identifier; and asupervisor module to carry out measurements, wherein said exportationmodule comprises means for transmitting at least one ticket of datapertaining to measurements carried out by said supervisor module to aserver, said ticket of data being according to said template and databeing related to said communication network administration information.11. The computer-readable memory as claimed in claim 10, wherein saidexportation module is designed to transmit: a data ticket comprising areference to a template, preceded, in the transmission, by the templatereferenced in said data ticket.